-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New podman::quadlet type for quadlet production #83
Conversation
@southalc time to look at this? |
This looks great! Would love to play with this. Not sure if it's intentional but some of your files/classes are named i.e |
That's indeed a typo from me - will correct. |
Been looking at this myself a bit today - I'd probably do it different than this
|
Thanks for your work and contribution to the project. I'm sorry about being slow to respond. I'm not as active here since changing jobs. |
I do indeed have a branch I'm playing with - more to do I'll update this one or provide a new one later this week.
voxpupuli ? |
@southalc everything stuffed into podman::quadlet now. Only container, volume and pod done but others easy enough to do for someone. |
Hi. A ping basically - voxpupuli ? There's a load of new stuff in the systemd module just released and we could rework a lot of whats here and make this module smaller - all the handling of user units is now in that module. |
Assuming at least podman 4.4.0 the new type `podman::quadlet` will create a quadlet unit files for a container, volume or pod which will in turn generate a service unit for managing the container, pod or volume. Boot root and rootless containers are supported. The included examples are operational however. Note that pod quadlets are only supported with podman 5.
I finally got around to this, although I see the voxpupuli module has since been stood up. Anyway, I implemented quadlets as a defined type where you can just define the parameters as a hash that gets converted to systemd unit files. This avoids the need to define a hard list of supported parameters and should allow the module to support future keywords to quadlet files with no module changes. I also switched over rootless users and services to use the systemd module instead of the collection of exec resources used previously. |
Assuming at least podman 4.4.0 the new type
podman::quadlet
will create a quadlet unit file for a container, volume or pod which will in turn generate a service unit for managing the resulting container, volume or pod.Note that pod quadlets require podman at least version 5.
Testing with a simple puppet file:
Results in a running container.